Office lunch is coordinated in group chats. Someone collects choices, chases latecomers, checks the budget and splits the bill, every day the office is full.
Consumer apps give each person a cart. Catering tools give the company control. Neither gives both.
organiser hours
₹9.9L
budget leakage
₹15.8L
employee hours deciding
₹33L
Total: about ₹59L a year
47 messages to order one lunch.
A typical team group chat, 10:30 to 11:45Budget, cutoff, restaurants and delivery point.
Individually, in a shared cart, or both.
Requests outside budget go to the organiser.
Locked at cutoff, grouped by restaurant and delivery time.
Switch between organiser, team lead and employee.
Menus, prices and restaurants are illustrative. Payments, Slack reminders and delivery are simulated. No order reaches a restaurant.
Includes 5 people
6 to 500 people
500+ · many countries
Proposed pilot measures: share of employees choosing before cutoff, budget exceptions per week, organiser minutes per day and on-time delivery. Targets, not results.
Proposed pilot measures. No traction is claimed.Risk: restaurant capacity at lunch peak → slot limits and partner confirmation
Slides after this point are supporting material, not part of the 12-slide main deck.
The selling points, as visitors see them.
Preferred meals reused automatically on chosen days.
An approved meal from past choices and dietary needs.
Daily, weekly or monthly schedules.
Out-of-policy requests routed to the organiser.
Items grouped by restaurant, availability and ETA.
Slack, email, WhatsApp and in-app.
office employees with a meal benefit (IT-BPM and GCCs)
a year in subscription revenue at about ₹127 per person (yearly rate)
3-year target: 1.5%, about 35,000 people
Global upside: companies with Indian centres roll one plan out across every office, with accounting per entity and country.
Measures to test, not results. harikrishna2004official@gmail.com